OpenEdge Development:<br />Translation Manager Preface

This book describes how to use the OpenEdge™ Translation Manager tool to manage the process of translating a 4GL application. It describes how the Translation Manager helps you through each step of the translation process, from the moment you receive the untranslated source code to the moment the completely translated application is running and ready to ship as a multi-lingual product.

Audience

This book is written for the translation project manager. The project manager is the person in a company who manages the entire process of translating 4GL applications into multiple languages. The project manager’s responsibilities include budgeting the translation process, hiring the translators, assembling the translation kits, monitoring the progress of the translators, answering questions regarding the application, reviewing translations, working with developers to create translatable applications, and building the final run-time code.

Organization

Describes techniques that you can share with software developers to make your company’s applications easier to translate.

Provides an overview of the Translation Management System and the tasks involved in using the Translation Manager and Visual Translator tools.

Describes how to organize a directory structure, set your PROPATH, start the Translation Manager tool, and connect to application databases.

Details how to create, open, and close a project database, select the current project, and select the source procedures you want to translate.

Explains how to prepare the data (text phrases and resource procedures) the translators will use to translate user-interface procedures.

Describes how to create, import, and export the lexical glossaries translators will use.

Describes how to build a language kit for the translator. It also describes how to send the language kit to the translators.

Details how to consolidate the translations and glossary entries from a translated language kit database into the project database.

Shows how to edit translations and glossary entries and scan for changed source files.

Provides answers to some common questions and describes solutions to common problems.

Provides reference information for the Translation Manager’s tab folders, menu bar, and tool bar.

Using this manual

This book is a guide to the Translation Manager tool. Although you can use it as a reference, it is structured so that each chapter builds on the previous chapters. Therefore, you will learn the most if you start at Chapter 1 and read through until the end.

Typographical conventions


Convention	Description
Bold	Bold typeface indicates commands or characters the user types, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, provides emphasis, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge™ key functions and generic keyboard keys; for example, GET and CTRL.
KEY1-KEY2	A hyphen between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL-X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
`Fixed width`	A fixed-width font is used in syntax statements, code examples, and for system output and filenames.
`Fixed-width italics`	Fixed-width italics indicate variables in syntax statements.
`Fixed-width bold`	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress® 4GL language keywords. Although these always are shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
Period (.) or colon (:)	All statements except `DO`, `FOR`, `FUNCTION`, `PROCEDURE`, and `REPEAT` end with a period. `DO`, `FOR`, `FUNCTION`, `PROCEDURE`, and `REPEAT` statements can end with either a period or a colon.
[ ]	Large brackets indicate the items within them are optional.
[ ]	Small brackets are part of the Progress 4GL language.
{ }	Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams.
{ }	Small braces are part of the Progress 4GL language. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure.
\|	A vertical bar indicates a choice.
...	Ellipses indicate repetition: you can choose one or more of the preceding items.

Examples of syntax descriptions

In this example, ACCUM is a keyword, and aggregate and expression are variables:

ACCUM `aggregate expression`

FOR is one of the statements that can end with either a period or a colon, as in this example:

FOR EACH Customer: DISPLAY Name. END.

In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional:

In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item:

A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example:

DISPLAY [ STREAM `stream` ] [ UNLESS-HIDDEN ] [ NO-ERROR ]

INITIAL [ `constant` [ , `constant` ] ]

{ `&argument-name` }

In this example, EACH, FIRST, and LAST are optional, but you can choose only one of them:

In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas:

PRESELECT [ EACH \| FIRST \| LAST ] `record-phrase`

MAXIMUM ( `expression` , `expression` [ , `expression` ] ... )

In this example, you must specify MESSAGE and at least one expression or SKIP [ (n) ], and any number of additional expression or SKIP [ ( n ) ] is allowed:

MESSAGE { `expression` \| SKIP [ ( `n` ) ] } ...

In this example, you must specify {include-file, then optionally any number of argument or &argument-name = "argument-value", and then terminate with }:

Long syntax descriptions split across lines

Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order.

Complex syntax descriptions with both required and optional elements

Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements).

{ `include-file` [ `argument` \| `&argument-name = "argument-value"` ] ... }

Syntax
WITH [ ACCUM `max-length` ] [ `expression` DOWN ] [ CENTERED ] [ `n` COLUMNS ] [ SIDE-LABELS ] [ STREAM-IO ]

In this example, ASSIGN requires either one or more field entries or one record. Options available with field or record are grouped with braces and brackets:

Syntax
ASSIGN { { [ FRAME `frame` ] { `field` [ = `expression` ] } [ WHEN `expression` ] } ... \| { `record` [ EXCEPT `field` ... ] } }

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Obtaining more information about OpenEdge messages

On Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

Preface

Purpose